Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d2c9e143bad1008932bf770263a1704c9a27c5768652bd6069ca9667c8d168c

Tx prefix hash: d1544558712e64e2fb60b28b94ae91811f300039b36ab364299a36f931ed1e27
Tx public key: b555a2eaaefa35c9043f5282e80901431a72a4f6a0f5e0a62f8d5755ff95702a
Timestamp: 1711279120 Timestamp [UCT]: 2024-03-24 11:18:40 Age [y:d:h:m:s]: 01:082:11:25:39
Block: 985275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319860 RingCT/type: yes/0
Extra: 01b555a2eaaefa35c9043f5282e80901431a72a4f6a0f5e0a62f8d5755ff95702a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5ee9e2f99272536281c0ed9da4a49d279b756b05718cc7f55996bd145d6031 0.600000000000 1445484 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": 985285, "vin": [ { "gen": { "height": 985275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5ee9e2f99272536281c0ed9da4a49d279b756b05718cc7f55996bd145d6031" } } ], "extra": [ 1, 181, 85, 162, 234, 174, 250, 53, 201, 4, 63, 82, 130, 232, 9, 1, 67, 26, 114, 164, 246, 160, 245, 224, 166, 47, 141, 87, 85, 255, 149, 112, 42, 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