Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b677eec169ef60bbc29ccb6176b1463f0ab4d9bc9d67af7ab0ee8d470246af1

Tx prefix hash: e208c8bbd46781cee9d9ae9ef2478bdd5e3ffa4b4ae18cb253fc607691b40c93
Tx public key: 794388bd88ec3556a51ddb636b4486db712e5bce532337b3ea324bff5cfee97c
Timestamp: 1719892569 Timestamp [UCT]: 2024-07-02 03:56:09 Age [y:d:h:m:s]: 01:129:09:11:33
Block: 1056661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351008 RingCT/type: yes/0
Extra: 01794388bd88ec3556a51ddb636b4486db712e5bce532337b3ea324bff5cfee97c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e2f87a61c7732d0fa59cc5e95b06a6c65325cc02f66216f9c556b926b1f9def 0.600000000000 1527078 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": 1056671, "vin": [ { "gen": { "height": 1056661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e2f87a61c7732d0fa59cc5e95b06a6c65325cc02f66216f9c556b926b1f9def" } } ], "extra": [ 1, 121, 67, 136, 189, 136, 236, 53, 86, 165, 29, 219, 99, 107, 68, 134, 219, 113, 46, 91, 206, 83, 35, 55, 179, 234, 50, 75, 255, 92, 254, 233, 124, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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