Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef39ec17d50bc415cf9be0ffac5b92c24c9c941ee72c8616f7e0a9b1f31d4f16

Tx prefix hash: f7892ea78278f011da86711fcbf695d92c89cfeca6b606fe37a1b9d9caca579f
Tx public key: 0fee63b10f783dc5a39363395b8acbc9ff68690d46f05e2442e01b1d75d8a8d9
Timestamp: 1717588268 Timestamp [UCT]: 2024-06-05 11:51:08 Age [y:d:h:m:s]: 00:283:22:00:22
Block: 1037565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202910 RingCT/type: yes/0
Extra: 010fee63b10f783dc5a39363395b8acbc9ff68690d46f05e2442e01b1d75d8a8d9021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a43b0116a6c90ca0ed85789b7ec142ee062337976ddc2cac83a151d4868775a 0.600000000000 1506110 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": 1037575, "vin": [ { "gen": { "height": 1037565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a43b0116a6c90ca0ed85789b7ec142ee062337976ddc2cac83a151d4868775a" } } ], "extra": [ 1, 15, 238, 99, 177, 15, 120, 61, 197, 163, 147, 99, 57, 91, 138, 203, 201, 255, 104, 105, 13, 70, 240, 94, 36, 66, 224, 27, 29, 117, 216, 168, 217, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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