Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d9b3a392ec673753fb1699abd6f78ca3842ed8b29441fc4fe2f867cdc3e96fe

Tx prefix hash: b9c9be51f7792a6f47907e74586f608bb1b760d2178f2150652ffd0efea8e969
Tx public key: f7b5a92269ed003aeb529408e6811d1e9d7e18b10f48f0a4701ca0d4754cd2ab
Timestamp: 1704591131 Timestamp [UCT]: 2024-01-07 01:32:11 Age [y:d:h:m:s]: 01:082:10:50:08
Block: 929783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320046 RingCT/type: yes/0
Extra: 01f7b5a92269ed003aeb529408e6811d1e9d7e18b10f48f0a4701ca0d4754cd2ab02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69fecacd45548f562a51d59d14a906d74b44a0512e44fdf073f401167982267a 0.600000000000 1387659 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": 929793, "vin": [ { "gen": { "height": 929783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69fecacd45548f562a51d59d14a906d74b44a0512e44fdf073f401167982267a" } } ], "extra": [ 1, 247, 181, 169, 34, 105, 237, 0, 58, 235, 82, 148, 8, 230, 129, 29, 30, 157, 126, 24, 177, 15, 72, 240, 164, 112, 28, 160, 212, 117, 76, 210, 171, 2, 17, 0, 0, 0, 1, 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