Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e6147a8014ced10ed669c58ad13ea28d6f33d31fd6f1a08d55789ac0c938f10

Tx prefix hash: f633128bd0da2e952f5697bb711e735e94002f6222c8eff571ad06b3c57bceb6
Tx public key: e7de3055092d2e35d4ab2c6df109ea8dacf0860cc17114b103c8c73ed8b63b7e
Timestamp: 1724911473 Timestamp [UCT]: 2024-08-29 06:04:33 Age [y:d:h:m:s]: 00:212:06:09:00
Block: 1098269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151558 RingCT/type: yes/0
Extra: 01e7de3055092d2e35d4ab2c6df109ea8dacf0860cc17114b103c8c73ed8b63b7e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f78dd54191ce64bd829b4f1082d38e6a59f2693a32a7c3e2c7474da10d807c2 0.600000000000 1573928 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": 1098279, "vin": [ { "gen": { "height": 1098269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f78dd54191ce64bd829b4f1082d38e6a59f2693a32a7c3e2c7474da10d807c2" } } ], "extra": [ 1, 231, 222, 48, 85, 9, 45, 46, 53, 212, 171, 44, 109, 241, 9, 234, 141, 172, 240, 134, 12, 193, 113, 20, 177, 3, 200, 199, 62, 216, 182, 59, 126, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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