Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cbb28a477a60581cfd99752406cb690c73cac6ad7a14084ca2fd183715158cd

Tx prefix hash: 92a4034d0e9c068a3ab52bc0ad4b93e36d42afa38155674cbe6668e62e77b51e
Tx public key: 1a348fb902f82a767cd20fd0134d6d727501f4cafceab5de6b5b1c8c186e2558
Timestamp: 1708628235 Timestamp [UCT]: 2024-02-22 18:57:15 Age [y:d:h:m:s]: 01:096:13:54:36
Block: 963280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330100 RingCT/type: yes/0
Extra: 011a348fb902f82a767cd20fd0134d6d727501f4cafceab5de6b5b1c8c186e255802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 560e5cc61b589430e8819c213207cc1563da5da039e515d288b39d9bb796a58a 0.600000000000 1422981 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": 963290, "vin": [ { "gen": { "height": 963280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "560e5cc61b589430e8819c213207cc1563da5da039e515d288b39d9bb796a58a" } } ], "extra": [ 1, 26, 52, 143, 185, 2, 248, 42, 118, 124, 210, 15, 208, 19, 77, 109, 114, 117, 1, 244, 202, 252, 234, 181, 222, 107, 91, 28, 140, 24, 110, 37, 88, 2, 17, 0, 0, 0, 2, 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