Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e4610d9a3429dba33b97e1083b6dc7f8288eaeb9fad7dfc4c2fa86870a3544

Tx prefix hash: 54f2e2b2b0965f4e10ec46b7983093bb2de2fa8132433ec58ed6f508e79858f7
Tx public key: 81c6e4cc0246d1d944a6733acd585a9edfddc5a08ee963bd3286a74a3f27388b
Timestamp: 1704900393 Timestamp [UCT]: 2024-01-10 15:26:33 Age [y:d:h:m:s]: 01:298:15:50:27
Block: 932364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472268 RingCT/type: yes/0
Extra: 0181c6e4cc0246d1d944a6733acd585a9edfddc5a08ee963bd3286a74a3f27388b0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e463ce37fe7846971f59bcccc4353fbf21fa18e59d434054dacab271269814fd 0.600000000000 1390296 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": 932374, "vin": [ { "gen": { "height": 932364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e463ce37fe7846971f59bcccc4353fbf21fa18e59d434054dacab271269814fd" } } ], "extra": [ 1, 129, 198, 228, 204, 2, 70, 209, 217, 68, 166, 115, 58, 205, 88, 90, 158, 223, 221, 197, 160, 142, 233, 99, 189, 50, 134, 167, 74, 63, 39, 56, 139, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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