Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7c771203775f60711e6dd78d6ed8cbdb9044f6ea1bfe0084a79bffb3a928c10

Tx prefix hash: bfc01f10a9af99c2a4c0a97339465b91b645e4cbe1cb9d14a21eb82b16e4519a
Tx public key: 05dcf7557c03061beeff24d6bfe76dd8301296a925afc67e4df24acad60f1e08
Timestamp: 1749736277 Timestamp [UCT]: 2025-06-12 13:51:17 Age [y:d:h:m:s]: 00:150:05:04:36
Block: 1303481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105074 RingCT/type: yes/0
Extra: 0105dcf7557c03061beeff24d6bfe76dd8301296a925afc67e4df24acad60f1e08021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 369631182aafe9614a73cfe9eb0c5f56c09df3f1a26e090f393d74837ad607f0 0.600000000000 1791062 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": 1303491, "vin": [ { "gen": { "height": 1303481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "369631182aafe9614a73cfe9eb0c5f56c09df3f1a26e090f393d74837ad607f0" } } ], "extra": [ 1, 5, 220, 247, 85, 124, 3, 6, 27, 238, 255, 36, 214, 191, 231, 109, 216, 48, 18, 150, 169, 37, 175, 198, 126, 77, 242, 74, 202, 214, 15, 30, 8, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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