Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d38589f6b0a6d939420c93b8e7531d4f5d755964800361864ec5a6f445ab8f84

Tx prefix hash: 17fb4bee76968f6d857d57204d5cb20336cd6773fab0353008d4a971b1f9359a
Tx public key: 4ffe3ee569f714f4fa1a81ba8226cc7f16dfd93de01cd970f8e1a44d3a987270
Timestamp: 1725292148 Timestamp [UCT]: 2024-09-02 15:49:08 Age [y:d:h:m:s]: 00:193:10:13:41
Block: 1101434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138098 RingCT/type: yes/0
Extra: 014ffe3ee569f714f4fa1a81ba8226cc7f16dfd93de01cd970f8e1a44d3a987270021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1832122882b4001c59e2d811739df6d315149636c405f8701d526508ca08bf5 0.600000000000 1577479 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": 1101444, "vin": [ { "gen": { "height": 1101434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1832122882b4001c59e2d811739df6d315149636c405f8701d526508ca08bf5" } } ], "extra": [ 1, 79, 254, 62, 229, 105, 247, 20, 244, 250, 26, 129, 186, 130, 38, 204, 127, 22, 223, 217, 61, 224, 28, 217, 112, 248, 225, 164, 77, 58, 152, 114, 112, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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