Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f40de8638ef51ee912835245c10cc2f152fe30381189b8e25cfed5330224485f

Tx prefix hash: 0caf52116c366bd6e13d90f8b1596f0ec2c5bcf8ac4865f7e0231fd12270f846
Tx public key: 697bfd7af128f3c36c715405a469a8f98b1b0c918d87ed691127278661ab62f7
Timestamp: 1584527116 Timestamp [UCT]: 2020-03-18 10:25:16 Age [y:d:h:m:s]: 05:076:01:37:18
Block: 84911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1210698 RingCT/type: yes/0
Extra: 01697bfd7af128f3c36c715405a469a8f98b1b0c918d87ed691127278661ab62f702110000000548d4d863000000000000000000

1 output(s) for total of 321.122004144000 dcy

stealth address amount amount idx
00: 2cae8db330bbdcc9c0fabf79eb514d55d18e4b07fdabcb893aec5fcaa1a376c5 321.122004144000 153689 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": 84921, "vin": [ { "gen": { "height": 84911 } } ], "vout": [ { "amount": 321122004144, "target": { "key": "2cae8db330bbdcc9c0fabf79eb514d55d18e4b07fdabcb893aec5fcaa1a376c5" } } ], "extra": [ 1, 105, 123, 253, 122, 241, 40, 243, 195, 108, 113, 84, 5, 164, 105, 168, 249, 139, 27, 12, 145, 141, 135, 237, 105, 17, 39, 39, 134, 97, 171, 98, 247, 2, 17, 0, 0, 0, 5, 72, 212, 216, 99, 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