Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c52f4a1061e970ff1ff4fe5a59baf0910e3c79222d85a07aeb8791f613adf4e9

Tx prefix hash: b53271ca1ac166671770de6be22b4c8f48c1e67c795becaf3a18fa3218815667
Tx public key: 9aa3d4f21245cf2157029d5afdaec2acee1f57ead91456b25a68607ceb720de5
Timestamp: 1744414913 Timestamp [UCT]: 2025-04-11 23:41:53 Age [y:d:h:m:s]: 00:271:17:45:49
Block: 1259466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192012 RingCT/type: yes/0
Extra: 019aa3d4f21245cf2157029d5afdaec2acee1f57ead91456b25a68607ceb720de5021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ec14534d0e60cbc5d7ea0f1c76c529a5d7744755696d3ef4a62d3a86e09fa7e 0.600000000000 1746609 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": 1259476, "vin": [ { "gen": { "height": 1259466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ec14534d0e60cbc5d7ea0f1c76c529a5d7744755696d3ef4a62d3a86e09fa7e" } } ], "extra": [ 1, 154, 163, 212, 242, 18, 69, 207, 33, 87, 2, 157, 90, 253, 174, 194, 172, 238, 31, 87, 234, 217, 20, 86, 178, 90, 104, 96, 124, 235, 114, 13, 229, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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