Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a206ac1e7fcdcb9c78bdefab86619995199ccec0d62548de5674e13cf16a7e04

Tx prefix hash: 35b752ac1787a39d65819dc701556a0fc8b7ea2a779470dff4df73cf1eabdfde
Tx public key: dbc64c31405b49a73c70bbad92ace8c30f534e39b64d3f098ae99204b850dcd4
Timestamp: 1709774047 Timestamp [UCT]: 2024-03-07 01:14:07 Age [y:d:h:m:s]: 01:101:11:37:56
Block: 972785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333466 RingCT/type: yes/0
Extra: 01dbc64c31405b49a73c70bbad92ace8c30f534e39b64d3f098ae99204b850dcd402110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56b4e4c4e60325795ef2c79a6b0998cd56e65ec426e7e12bf35ccadbf9ae855f 0.600000000000 1432704 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": 972795, "vin": [ { "gen": { "height": 972785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56b4e4c4e60325795ef2c79a6b0998cd56e65ec426e7e12bf35ccadbf9ae855f" } } ], "extra": [ 1, 219, 198, 76, 49, 64, 91, 73, 167, 60, 112, 187, 173, 146, 172, 232, 195, 15, 83, 78, 57, 182, 77, 63, 9, 138, 233, 146, 4, 184, 80, 220, 212, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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