Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d217c7ef2a7d0b5214dd25ca0dcac1969bd3e46dc5cffe488a20c7fd07a388e

Tx prefix hash: 9c5edd15e83d5205498749b3df9d5eb49c2e8291de5d6237a0641d2030577cb6
Tx public key: 120e940e0a2706e5d794c5518b48ef3ebb43f5c43eb5797e57be65c1745b8100
Timestamp: 1722821625 Timestamp [UCT]: 2024-08-05 01:33:45 Age [y:d:h:m:s]: 00:256:05:30:10
Block: 1080941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183039 RingCT/type: yes/0
Extra: 01120e940e0a2706e5d794c5518b48ef3ebb43f5c43eb5797e57be65c1745b8100021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b55407fc2b00d4f4be29783e745d84aa7e0ad7d76370e1852eb5c07f3e18a48 0.600000000000 1554496 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": 1080951, "vin": [ { "gen": { "height": 1080941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b55407fc2b00d4f4be29783e745d84aa7e0ad7d76370e1852eb5c07f3e18a48" } } ], "extra": [ 1, 18, 14, 148, 14, 10, 39, 6, 229, 215, 148, 197, 81, 139, 72, 239, 62, 187, 67, 245, 196, 62, 181, 121, 126, 87, 190, 101, 193, 116, 91, 129, 0, 2, 17, 0, 0, 0, 1, 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