Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07e49e3297c76d88dc1bd5a0f66a5d94678941921124a5d67978e27d20fc824b

Tx prefix hash: cd3e26b13591585aba8ca47f3af677d51718fb4afb2dae0adfcc136d40e7e3e2
Tx public key: cda2f56d6e62b1c0e6b4fb1cc330c095bde398b06fa6a0f2b78a84f21dfabd25
Timestamp: 1711405411 Timestamp [UCT]: 2024-03-25 22:23:31 Age [y:d:h:m:s]: 01:226:13:57:04
Block: 986323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420603 RingCT/type: yes/0
Extra: 01cda2f56d6e62b1c0e6b4fb1cc330c095bde398b06fa6a0f2b78a84f21dfabd2502110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b837157f50bb23a576a30fe4ed8ebbbe9d704c8a9875e22978f6f8828b2e642 0.600000000000 1446552 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": 986333, "vin": [ { "gen": { "height": 986323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b837157f50bb23a576a30fe4ed8ebbbe9d704c8a9875e22978f6f8828b2e642" } } ], "extra": [ 1, 205, 162, 245, 109, 110, 98, 177, 192, 230, 180, 251, 28, 195, 48, 192, 149, 189, 227, 152, 176, 111, 166, 160, 242, 183, 138, 132, 242, 29, 250, 189, 37, 2, 17, 0, 0, 0, 4, 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