Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aede4d7b64cb65d02d3ac1a909392611817405a25227ee8769b70d6cfa29c94b

Tx prefix hash: 808c18dda204da8e0ed32aa8fdadd0ecef5ff8b27e0517d089bb2aac6d5c5339
Tx public key: 58858bcf4c4a9a62d61a06f46d9c34a7e5bcac2fd7d157f2fc22340017a8d503
Timestamp: 1706567519 Timestamp [UCT]: 2024-01-29 22:31:59 Age [y:d:h:m:s]: 01:059:08:31:13
Block: 946173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303494 RingCT/type: yes/0
Extra: 0158858bcf4c4a9a62d61a06f46d9c34a7e5bcac2fd7d157f2fc22340017a8d5030211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fbbc7c937fa36e313f1e68d96960f717bbddf5ca42a0e826630cd02a0769715 0.600000000000 1404503 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": 946183, "vin": [ { "gen": { "height": 946173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fbbc7c937fa36e313f1e68d96960f717bbddf5ca42a0e826630cd02a0769715" } } ], "extra": [ 1, 88, 133, 139, 207, 76, 74, 154, 98, 214, 26, 6, 244, 109, 156, 52, 167, 229, 188, 172, 47, 215, 209, 87, 242, 252, 34, 52, 0, 23, 168, 213, 3, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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