Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cfdd4a73903a3019aab51aa47de9dd80927318dcfcbc784d6af746232438ca0d

Tx prefix hash: e39810992a29c731c168c2b959f64fa6b668501fe0d0e36451482765bef5f0c0
Tx public key: 14e88cd54d471df62a59cdbe86f91901627c6e4905f984df3747542b1fd8769a
Timestamp: 1585417305 Timestamp [UCT]: 2020-03-28 17:41:45 Age [y:d:h:m:s]: 04:245:13:58:53
Block: 88964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074442 RingCT/type: yes/0
Extra: 0114e88cd54d471df62a59cdbe86f91901627c6e4905f984df3747542b1fd8769a021100000014a86a1a65000000000000000000

1 output(s) for total of 311.333686457000 dcy

stealth address amount amount idx
00: 7be0669f95b901f1c00535dafb24610a446ba91798b71e173f603edacb9dc2ef 311.333686457000 159792 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 88974, "vin": [ { "gen": { "height": 88964 } } ], "vout": [ { "amount": 311333686457, "target": { "key": "7be0669f95b901f1c00535dafb24610a446ba91798b71e173f603edacb9dc2ef" } } ], "extra": [ 1, 20, 232, 140, 213, 77, 71, 29, 246, 42, 89, 205, 190, 134, 249, 25, 1, 98, 124, 110, 73, 5, 249, 132, 223, 55, 71, 84, 43, 31, 216, 118, 154, 2, 17, 0, 0, 0, 20, 168, 106, 26, 101, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8