Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1641c0728da748226f5ac03fcd1caeb80176d2bba5cc7a644dfa89ee9900ef73

Tx prefix hash: d43dbd29f9d2a6745fd1169e4e59d9005031b08e436594293ddfb10d1534f237
Tx public key: 8b0122d0f3fe35d1728bde0c74f66ba3e20fa3351a62d098ff7b904c0d632bd3
Timestamp: 1698636915 Timestamp [UCT]: 2023-10-30 03:35:15 Age [y:d:h:m:s]: 01:214:09:41:24
Block: 880661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414282 RingCT/type: yes/0
Extra: 018b0122d0f3fe35d1728bde0c74f66ba3e20fa3351a62d098ff7b904c0d632bd302110000000afaf35c9c000000000000000000

1 output(s) for total of 0.741317989000 dcy

stealth address amount amount idx
00: 1edbd59ec84bc4be26bb5472740e31dc555605319c4f1ec686f25d20d8def45d 0.741317989000 1336225 of 0

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": 880671, "vin": [ { "gen": { "height": 880661 } } ], "vout": [ { "amount": 741317989, "target": { "key": "1edbd59ec84bc4be26bb5472740e31dc555605319c4f1ec686f25d20d8def45d" } } ], "extra": [ 1, 139, 1, 34, 208, 243, 254, 53, 209, 114, 139, 222, 12, 116, 246, 107, 163, 226, 15, 163, 53, 26, 98, 208, 152, 255, 123, 144, 76, 13, 99, 43, 211, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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