Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e6b9eed5d07e66b1ea6c6974ef2344b4d8f7bee572a35848d1ed092c0459a8

Tx prefix hash: 094cb502ca7ff0c345950d20d8ce6ef680994b59b7eb32c7e62fd88c1542af91
Tx public key: 57829167641ba02b129c43ab5062354b6360298e3bbfbfb32ac3423e8f5e3a1b
Timestamp: 1730630193 Timestamp [UCT]: 2024-11-03 10:36:33 Age [y:d:h:m:s]: 00:206:11:15:52
Block: 1145604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147434 RingCT/type: yes/0
Extra: 0157829167641ba02b129c43ab5062354b6360298e3bbfbfb32ac3423e8f5e3a1b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f11ada4ba18e3851a1b0b6fb8e7f0d95f9fd7bf8f88512aab203715f4690a187 0.600000000000 1630079 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": 1145614, "vin": [ { "gen": { "height": 1145604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f11ada4ba18e3851a1b0b6fb8e7f0d95f9fd7bf8f88512aab203715f4690a187" } } ], "extra": [ 1, 87, 130, 145, 103, 100, 27, 160, 43, 18, 156, 67, 171, 80, 98, 53, 75, 99, 96, 41, 142, 59, 191, 191, 179, 42, 195, 66, 62, 143, 94, 58, 27, 2, 17, 0, 0, 0, 3, 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