Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97d5452c979050391e2dd211e9e3b123cd0a0179127d50d59f25aa16d0b6ca63

Tx prefix hash: 12846a7fab172c6f03d1e1c9a3c22278ef44a014aeeb1d54003d30bd24a4e4db
Tx public key: 929e69f26b4ce97001fe0039a98ad3c29e03f58c01cdb91575ba6e1d77f7284d
Timestamp: 1706353648 Timestamp [UCT]: 2024-01-27 11:07:28 Age [y:d:h:m:s]: 01:080:20:43:32
Block: 944394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318886 RingCT/type: yes/0
Extra: 01929e69f26b4ce97001fe0039a98ad3c29e03f58c01cdb91575ba6e1d77f7284d02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0785a27dc2feafcbdbf7c52356194562a67d87723c8eb4fdbd83961e95b78785 0.600000000000 1402630 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": 944404, "vin": [ { "gen": { "height": 944394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0785a27dc2feafcbdbf7c52356194562a67d87723c8eb4fdbd83961e95b78785" } } ], "extra": [ 1, 146, 158, 105, 242, 107, 76, 233, 112, 1, 254, 0, 57, 169, 138, 211, 194, 158, 3, 245, 140, 1, 205, 185, 21, 117, 186, 110, 29, 119, 247, 40, 77, 2, 17, 0, 0, 0, 5, 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