Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffbdadc26485cf6f17ecfc3aeed10dbc68b6641bd93f51704730625a8e9fe196

Tx prefix hash: 890a912bd0bf1b7d2e01952b47f1ce48f6037085dfe654ee3b2e8cb80a3842d6
Tx public key: fc3a5d7ee04a67dc9ac549f841a0b8821c548a460a85c96ef4a93391afb9eaf2
Timestamp: 1582434234 Timestamp [UTC]: 2020-02-23 05:03:54 Age [y:d:h:m:s]: 06:270:20:09:22
Block: 70593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1610936 RingCT/type: yes/0
Extra: 01fc3a5d7ee04a67dc9ac549f841a0b8821c548a460a85c96ef4a93391afb9eaf2021100000004d81c26c0000000000000000000

1 output(s) for total of 0.358176335816 xmr

stealth address amount amount idx tag
00: 967320f8112970c9567431527bd02c673fcca4e075041e50f85f0b1bc8ae3858 0.358176335816 130447 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 dinastycoin-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": 70603, "vin": [ { "gen": { "height": 70593 } } ], "vout": [ { "amount": 358176335816, "target": { "key": "967320f8112970c9567431527bd02c673fcca4e075041e50f85f0b1bc8ae3858" } } ], "extra": [ 1, 252, 58, 93, 126, 224, 74, 103, 220, 154, 197, 73, 248, 65, 160, 184, 130, 28, 84, 138, 70, 10, 133, 201, 110, 244, 169, 51, 145, 175, 185, 234, 242, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: