Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61e38125bc1fa99431cbb1fff816cb06cdccb96b757c1c461f13c22b73429e34

Tx prefix hash: bc500860ebb5df7ed16d576ce00564ed0bf297d34a4c63c384840c64f8ac4c80
Tx public key: ccbb5956d9fdc07abc939976b34e6fe6b315aec4b5c5829e6b7956bdd3630546
Timestamp: 1722598616 Timestamp [UCT]: 2024-08-02 11:36:56 Age [y:d:h:m:s]: 00:178:07:42:25
Block: 1079098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127333 RingCT/type: yes/0
Extra: 01ccbb5956d9fdc07abc939976b34e6fe6b315aec4b5c5829e6b7956bdd363054602110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3b6267e002dfc3fe4baa444a6baf1dee1ae8f070e4020e058eb2417b05fa08a 0.600000000000 1551907 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": 1079108, "vin": [ { "gen": { "height": 1079098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3b6267e002dfc3fe4baa444a6baf1dee1ae8f070e4020e058eb2417b05fa08a" } } ], "extra": [ 1, 204, 187, 89, 86, 217, 253, 192, 122, 188, 147, 153, 118, 179, 78, 111, 230, 179, 21, 174, 196, 181, 197, 130, 158, 107, 121, 86, 189, 211, 99, 5, 70, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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