Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29180be9ca45ba424475b668600ff6957d6a61f08b17bbfa502c175efa7800a5

Tx prefix hash: 7f9c6591e90f143a5a793d995a1b34f3ce45ac236dfe65d2b8646535092fbd24
Tx public key: 654f1f9b965d0fdb20f7d114c169c7bed88fda395dc1b11a32c908aeb52e591f
Timestamp: 1709817001 Timestamp [UCT]: 2024-03-07 13:10:01 Age [y:d:h:m:s]: 01:070:13:26:44
Block: 973146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311442 RingCT/type: yes/0
Extra: 01654f1f9b965d0fdb20f7d114c169c7bed88fda395dc1b11a32c908aeb52e591f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6909e0e2c6bf36c970a6c870eb9d783ffa5afdb38bbe21e30748d09c2ddbb651 0.600000000000 1433079 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": 973156, "vin": [ { "gen": { "height": 973146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6909e0e2c6bf36c970a6c870eb9d783ffa5afdb38bbe21e30748d09c2ddbb651" } } ], "extra": [ 1, 101, 79, 31, 155, 150, 93, 15, 219, 32, 247, 209, 20, 193, 105, 199, 190, 216, 143, 218, 57, 93, 193, 177, 26, 50, 201, 8, 174, 181, 46, 89, 31, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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