Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea58c6baa36b4d557211d37519ac640e8d66c9966e6c231f354be4e15a03dda2

Tx prefix hash: 841c25359362f1702091f4ad6b1263160d878bcac3f7070ec0258f144d63c2dd
Tx public key: d4f4f971ddebf63dcbe986b60a5acb2ebe53c74d0c98adf530a806689b29f8d3
Timestamp: 1764218378 Timestamp [UCT]: 2025-11-27 04:39:38 Age [y:d:h:m:s]: 00:025:21:54:51
Block: 1421018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18559 RingCT/type: yes/0
Extra: 01d4f4f971ddebf63dcbe986b60a5acb2ebe53c74d0c98adf530a806689b29f8d30211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae81813b0cfe225481ee5455cbf3e77baf703f7a0b987f891be896114d03164c 0.600000000000 1909573 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": 1421028, "vin": [ { "gen": { "height": 1421018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae81813b0cfe225481ee5455cbf3e77baf703f7a0b987f891be896114d03164c" } } ], "extra": [ 1, 212, 244, 249, 113, 221, 235, 246, 61, 203, 233, 134, 182, 10, 90, 203, 46, 190, 83, 199, 77, 12, 152, 173, 245, 48, 168, 6, 104, 155, 41, 248, 211, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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