Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e29cf67e8b9ef3bf76ea292e7d9ad5fdb4594c9261a710158de3c4096b1727c2

Tx prefix hash: f28d11c25ebfc84127eba63e4db646818550cfffcaeef6501dcc531b15d9fe83
Tx public key: bd215ca79bb2912d4db03806302abdce21cd8fda2c253e2ac494c2b2b4f58727
Timestamp: 1702537899 Timestamp [UCT]: 2023-12-14 07:11:39 Age [y:d:h:m:s]: 01:161:15:05:50
Block: 912783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376697 RingCT/type: yes/0
Extra: 01bd215ca79bb2912d4db03806302abdce21cd8fda2c253e2ac494c2b2b4f58727021100000006faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a0cca4c13ca4ae93dcd0ab8d9c9917216479a1e7a923d155e3eea4fbce86485 0.600000000000 1370019 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": 912793, "vin": [ { "gen": { "height": 912783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a0cca4c13ca4ae93dcd0ab8d9c9917216479a1e7a923d155e3eea4fbce86485" } } ], "extra": [ 1, 189, 33, 92, 167, 155, 178, 145, 45, 77, 176, 56, 6, 48, 42, 189, 206, 33, 205, 143, 218, 44, 37, 62, 42, 196, 148, 194, 178, 180, 245, 135, 39, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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