Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91235e9eb13477b8e487ee94fc9c90dfc704402f5b8b18925beee089c977f317

Tx prefix hash: 530ec9b566bf71bb7767e4ae3b444787e32a1594740c161f72ac1363ee7139da
Tx public key: bcbffa3e01c5b3e2aef460021162c23ed8db3a9d6e0d8631fb66b5d58527a524
Timestamp: 1744153812 Timestamp [UCT]: 2025-04-08 23:10:12 Age [y:d:h:m:s]: 00:182:08:39:50
Block: 1257294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128010 RingCT/type: yes/0
Extra: 01bcbffa3e01c5b3e2aef460021162c23ed8db3a9d6e0d8631fb66b5d58527a524021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f430bc62fae91d9cab947e3ffa90ca6421dcbe23d30244db5b14e3d888efb2e 0.600000000000 1744413 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": 1257304, "vin": [ { "gen": { "height": 1257294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f430bc62fae91d9cab947e3ffa90ca6421dcbe23d30244db5b14e3d888efb2e" } } ], "extra": [ 1, 188, 191, 250, 62, 1, 197, 179, 226, 174, 244, 96, 2, 17, 98, 194, 62, 216, 219, 58, 157, 110, 13, 134, 49, 251, 102, 181, 213, 133, 39, 165, 36, 2, 17, 0, 0, 0, 5, 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