Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90975a7de5b1a3ff73bed7c1523358753643937f19a4a763e601548754cd69a7

Tx prefix hash: 7ef01ed0f9d53e6375c842db150520ee66db3b18f266b3e41b282a69a8c924d5
Tx public key: 6f7c9d1568a9b8576ac09fea49c30228c2eba6744bc3406957c08d17d1fecd25
Timestamp: 1718683928 Timestamp [UCT]: 2024-06-18 04:12:08 Age [y:d:h:m:s]: 01:145:20:31:42
Block: 1046647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362799 RingCT/type: yes/0
Extra: 016f7c9d1568a9b8576ac09fea49c30228c2eba6744bc3406957c08d17d1fecd250211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25d78173c44f32c50d68ea10f692bbaef831a2d1c7d9b7a62be306d0c1dc0796 0.600000000000 1516464 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": 1046657, "vin": [ { "gen": { "height": 1046647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25d78173c44f32c50d68ea10f692bbaef831a2d1c7d9b7a62be306d0c1dc0796" } } ], "extra": [ 1, 111, 124, 157, 21, 104, 169, 184, 87, 106, 192, 159, 234, 73, 195, 2, 40, 194, 235, 166, 116, 75, 195, 64, 105, 87, 192, 141, 23, 209, 254, 205, 37, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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