Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb0f3e554fc2558fb778de33bb993a3f7ad96989663d36a6186ad9a199bef24

Tx prefix hash: 8ef2e2e291f332f84bd85d8e9fea7a02634b8cb65b82fdd531bf2af0f5311f2b
Tx public key: 5cf9939e7a15d886704389316442795681df5837c4e96ebbd08d0d090d0c1b02
Timestamp: 1702449513 Timestamp [UCT]: 2023-12-13 06:38:33 Age [y:d:h:m:s]: 01:111:02:25:12
Block: 912074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340509 RingCT/type: yes/0
Extra: 015cf9939e7a15d886704389316442795681df5837c4e96ebbd08d0d090d0c1b0202110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e9adb96e41648274b4b23387e1c80c0d24c44333b4b37503b160471e4cc4ab8 0.600000000000 1369292 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": 912084, "vin": [ { "gen": { "height": 912074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e9adb96e41648274b4b23387e1c80c0d24c44333b4b37503b160471e4cc4ab8" } } ], "extra": [ 1, 92, 249, 147, 158, 122, 21, 216, 134, 112, 67, 137, 49, 100, 66, 121, 86, 129, 223, 88, 55, 196, 233, 110, 187, 208, 141, 13, 9, 13, 12, 27, 2, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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