Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f039b2d4da65add7880d607252c83f878c08e6840325451c51a48a61a387e5e

Tx prefix hash: 625bd8cf354c3544e52ddd072291f93275a4cc0ad682f5b4d5afdfec4b911d11
Tx public key: 1cb5fa997fcd51ede577109ea0941f8e65df594bf5aeb73dba142a1f1eee1e09
Timestamp: 1680978942 Timestamp [UCT]: 2023-04-08 18:35:42 Age [y:d:h:m:s]: 01:364:06:58:01
Block: 734348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521583 RingCT/type: yes/0
Extra: 011cb5fa997fcd51ede577109ea0941f8e65df594bf5aeb73dba142a1f1eee1e090211000000025029cbac000000000000000000

1 output(s) for total of 2.263604037000 dcy

stealth address amount amount idx
00: 642ed1d08f17dd96efa5843238ff3a0dbc4a0df4834fa252589d7c218340f9f9 2.263604037000 1180539 of 0

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": 734358, "vin": [ { "gen": { "height": 734348 } } ], "vout": [ { "amount": 2263604037, "target": { "key": "642ed1d08f17dd96efa5843238ff3a0dbc4a0df4834fa252589d7c218340f9f9" } } ], "extra": [ 1, 28, 181, 250, 153, 127, 205, 81, 237, 229, 119, 16, 158, 160, 148, 31, 142, 101, 223, 89, 75, 245, 174, 183, 61, 186, 20, 42, 31, 30, 238, 30, 9, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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