Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 749b9a1c201942cb6db4933e9b8f9f8766bd01b3091559ec1500a52bc6c34e78

Tx prefix hash: d050a70cb277e2d983f76ef39b7fb70e8989da09885d089b9819dcc11b067f1d
Tx public key: 88bb4c8fb1fafd8e55ea8fcaa0a89578fbc96c774402338a00bf45261b799952
Timestamp: 1727408860 Timestamp [UCT]: 2024-09-27 03:47:40 Age [y:d:h:m:s]: 00:058:14:56:07
Block: 1118981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41890 RingCT/type: yes/0
Extra: 0188bb4c8fb1fafd8e55ea8fcaa0a89578fbc96c774402338a00bf45261b79995202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7396385a02257a026913aa4a317916d226aa875ffbe8d8f114c5b1f4867ccde2 0.600000000000 1600364 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": 1118991, "vin": [ { "gen": { "height": 1118981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7396385a02257a026913aa4a317916d226aa875ffbe8d8f114c5b1f4867ccde2" } } ], "extra": [ 1, 136, 187, 76, 143, 177, 250, 253, 142, 85, 234, 143, 202, 160, 168, 149, 120, 251, 201, 108, 119, 68, 2, 51, 138, 0, 191, 69, 38, 27, 121, 153, 82, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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