Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5690d87da4449295e4c09c7e9ea738ce02d1b613f6c35f4304cd06242b417392

Tx prefix hash: 50fdf744b302a01912455c2daa3da584bc924ec3bf07f6101b412789ef52d5b9
Tx public key: aabcc7d67d841ebdd7b171d2593c8c1dd1cbab8b1f6635c923a460aee2c413fc
Timestamp: 1736526535 Timestamp [UCT]: 2025-01-10 16:28:55 Age [y:d:h:m:s]: 00:068:08:20:59
Block: 1194422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48649 RingCT/type: yes/0
Extra: 01aabcc7d67d841ebdd7b171d2593c8c1dd1cbab8b1f6635c923a460aee2c413fc0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ba449f1651248fb134e93ddb7f908b909223c55aeaab5a9eec379760f0e250e 0.600000000000 1680993 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": 1194432, "vin": [ { "gen": { "height": 1194422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ba449f1651248fb134e93ddb7f908b909223c55aeaab5a9eec379760f0e250e" } } ], "extra": [ 1, 170, 188, 199, 214, 125, 132, 30, 189, 215, 177, 113, 210, 89, 60, 140, 29, 209, 203, 171, 139, 31, 102, 53, 201, 35, 164, 96, 174, 226, 196, 19, 252, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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