Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241d91da7275248100a1b438ae3dc988d9fbd5cba95997a04c96fb01dbbbf37b

Tx prefix hash: b49c6fc2f1ad1f4b76edb90af9526611e2dbd7bfef799e48ba0a6ba010d78274
Tx public key: c2f63bdabe5ffbc53f733b4e970be4062d1525b926ed93103aef95d80e7fbbd9
Timestamp: 1706401676 Timestamp [UCT]: 2024-01-28 00:27:56 Age [y:d:h:m:s]: 01:067:01:42:36
Block: 944795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309013 RingCT/type: yes/0
Extra: 01c2f63bdabe5ffbc53f733b4e970be4062d1525b926ed93103aef95d80e7fbbd902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e791a380c9aff897d5171094407c9ee1dbcc537d9da76352dabf7bb6012be9e 0.600000000000 1403081 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": 944805, "vin": [ { "gen": { "height": 944795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e791a380c9aff897d5171094407c9ee1dbcc537d9da76352dabf7bb6012be9e" } } ], "extra": [ 1, 194, 246, 59, 218, 190, 95, 251, 197, 63, 115, 59, 78, 151, 11, 228, 6, 45, 21, 37, 185, 38, 237, 147, 16, 58, 239, 149, 216, 14, 127, 187, 217, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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