Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cc71fa2f636dcb209ccbe3ed98da4c50abb5ceadb64b421ebc73219c184e0f9

Tx prefix hash: 53456a6b1ccf98b96abd65c8ed11e16eee90a7a61783b6f694c4c48dc166d3d0
Tx public key: 937ddd31e872534b9e12cc46c2b735657309e74a0e0616905fae930a01f2cc47
Timestamp: 1682522828 Timestamp [UCT]: 2023-04-26 15:27:08 Age [y:d:h:m:s]: 01:345:00:51:50
Block: 747101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507853 RingCT/type: yes/0
Extra: 01937ddd31e872534b9e12cc46c2b735657309e74a0e0616905fae930a01f2cc4702110000000175e3f0e9000000000000000000

1 output(s) for total of 2.053735253000 dcy

stealth address amount amount idx
00: 372f808fae2e6628069740a872f61cf57425d6f2177ba03ea7a504bedd4ba784 2.053735253000 1194738 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 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": 747111, "vin": [ { "gen": { "height": 747101 } } ], "vout": [ { "amount": 2053735253, "target": { "key": "372f808fae2e6628069740a872f61cf57425d6f2177ba03ea7a504bedd4ba784" } } ], "extra": [ 1, 147, 125, 221, 49, 232, 114, 83, 75, 158, 18, 204, 70, 194, 183, 53, 101, 115, 9, 231, 74, 14, 6, 22, 144, 95, 174, 147, 10, 1, 242, 204, 71, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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