Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 247f71ed8c9785d431a306d490ec9df202410b4dcfcdb0706fb5af43ec1d005c

Tx prefix hash: 89601cb4bc01be3e926a0ed5138bf7f97da82e9a16ab8b024570dc11b620e8e1
Tx public key: a86ecf4916c7c66b96d13ddf8b2b02d2b1e2c9da25d50edc4f96b1d5155b9b81
Timestamp: 1721867006 Timestamp [UCT]: 2024-07-25 00:23:26 Age [y:d:h:m:s]: 00:307:20:03:47
Block: 1073034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219970 RingCT/type: yes/0
Extra: 01a86ecf4916c7c66b96d13ddf8b2b02d2b1e2c9da25d50edc4f96b1d5155b9b81021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cf1a076f8620c92e2e84e56fafdf525f056b3f02c52420429adaef9e9ba0c0c 0.600000000000 1545533 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": 1073044, "vin": [ { "gen": { "height": 1073034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cf1a076f8620c92e2e84e56fafdf525f056b3f02c52420429adaef9e9ba0c0c" } } ], "extra": [ 1, 168, 110, 207, 73, 22, 199, 198, 107, 150, 209, 61, 223, 139, 43, 2, 210, 177, 226, 201, 218, 37, 213, 14, 220, 79, 150, 177, 213, 21, 91, 155, 129, 2, 17, 0, 0, 0, 6, 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