Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66f01bd1cf9215817afbaee54a60d616115f29edf2b2fda305f897154a256699

Tx prefix hash: 5a4f1a16678413dfa8baf8ebb344897cf5c868ab5c52f62fa812a695d079b418
Tx public key: b6317254534b92fd9a5137863d3be6b269ab0a95d32919a4a18bd167167076f4
Timestamp: 1725721539 Timestamp [UCT]: 2024-09-07 15:05:39 Age [y:d:h:m:s]: 00:107:11:57:25
Block: 1104999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76881 RingCT/type: yes/0
Extra: 01b6317254534b92fd9a5137863d3be6b269ab0a95d32919a4a18bd167167076f4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cb0a9c4c8bc43cf450263aafb41db6b0aba3465efc0983fbef074e7b3d8a352 0.600000000000 1582334 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": 1105009, "vin": [ { "gen": { "height": 1104999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cb0a9c4c8bc43cf450263aafb41db6b0aba3465efc0983fbef074e7b3d8a352" } } ], "extra": [ 1, 182, 49, 114, 84, 83, 75, 146, 253, 154, 81, 55, 134, 61, 59, 230, 178, 105, 171, 10, 149, 211, 41, 25, 164, 161, 139, 209, 103, 22, 112, 118, 244, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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