Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ef5654e1c870882158a86b41721613b6596c4d0bb2b3837352d3be0c6e3669f

Tx prefix hash: 99966b2c042cf29102c672cbef43b3c1db3cc2498ebf6ece838a327bad90491e
Tx public key: 2c2da47de8efb5684f29d471dc4944c4b10df46dfd2b2b2095f08d3800863f7f
Timestamp: 1704444270 Timestamp [UCT]: 2024-01-05 08:44:30 Age [y:d:h:m:s]: 01:100:18:19:19
Block: 928573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333134 RingCT/type: yes/0
Extra: 012c2da47de8efb5684f29d471dc4944c4b10df46dfd2b2b2095f08d3800863f7f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 887051e1b96a2fc219a5189dab57e8295b93358090f46f7a5e918b4e107c0e19 0.600000000000 1386433 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": 928583, "vin": [ { "gen": { "height": 928573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "887051e1b96a2fc219a5189dab57e8295b93358090f46f7a5e918b4e107c0e19" } } ], "extra": [ 1, 44, 45, 164, 125, 232, 239, 181, 104, 79, 41, 212, 113, 220, 73, 68, 196, 177, 13, 244, 109, 253, 43, 43, 32, 149, 240, 141, 56, 0, 134, 63, 127, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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