Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c38b9add3ac7c6fc3f9c95a88d8063e754dd7f5b456ed67c61726a2613896065

Tx prefix hash: ee5d5574a1b57bbb175e838d828e49523281ff14fed2c7d198e18da71f3934a8
Tx public key: 4215a085f7f623017e43b77d20f1904bbdf5451cf21ef1bef12a7a0e6590c292
Timestamp: 1702366951 Timestamp [UCT]: 2023-12-12 07:42:31 Age [y:d:h:m:s]: 01:333:14:22:44
Block: 911379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497278 RingCT/type: yes/0
Extra: 014215a085f7f623017e43b77d20f1904bbdf5451cf21ef1bef12a7a0e6590c29202110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a432e7b4b0ca3acf4dc4825729e99b0607fd83de8fc8cac61af165da287f54c7 0.600000000000 1368579 of 15

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": 911389, "vin": [ { "gen": { "height": 911379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a432e7b4b0ca3acf4dc4825729e99b0607fd83de8fc8cac61af165da287f54c7" } } ], "extra": [ 1, 66, 21, 160, 133, 247, 246, 35, 1, 126, 67, 183, 125, 32, 241, 144, 75, 189, 245, 69, 28, 242, 30, 241, 190, 241, 42, 122, 14, 101, 144, 194, 146, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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