Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3112882317d66161e6ffc2cb76793ff6bf32d461b9326d1e28a815eab5a8341a

Tx prefix hash: 2959980da7d752f8456bb58d88068ea1f9fcdf18dacb18d81f8f75ec005f7f30
Tx public key: aae563e0ed9c405fa2973a295f2921a831fe4ae428313721dc4df655470f77d1
Timestamp: 1732268767 Timestamp [UCT]: 2024-11-22 09:46:07 Age [y:d:h:m:s]: 00:001:20:32:24
Block: 1159169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1325 RingCT/type: yes/0
Extra: 01aae563e0ed9c405fa2973a295f2921a831fe4ae428313721dc4df655470f77d1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9a789126fe0ce701b50ecd8f694edec12f5869a3506bdb9acd278d83d2272c3 0.600000000000 1644802 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": 1159179, "vin": [ { "gen": { "height": 1159169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9a789126fe0ce701b50ecd8f694edec12f5869a3506bdb9acd278d83d2272c3" } } ], "extra": [ 1, 170, 229, 99, 224, 237, 156, 64, 95, 162, 151, 58, 41, 95, 41, 33, 168, 49, 254, 74, 228, 40, 49, 55, 33, 220, 77, 246, 85, 71, 15, 119, 209, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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