Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37e4ce9ef0316e2b04e1858685858cd638c5b00078d207adce6f55353dd278d3

Tx prefix hash: cb65f2b7ef7a784c24db7615cb103b25c2f9fa041d5ccd31fb1a7ef02e899caf
Tx public key: d17137f003e7f8e5d6b809cafe8ff3b21abd669b6cca90bb6d2b19457f41a64e
Timestamp: 1705682573 Timestamp [UCT]: 2024-01-19 16:42:53 Age [y:d:h:m:s]: 01:085:23:27:22
Block: 938827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322558 RingCT/type: yes/0
Extra: 01d17137f003e7f8e5d6b809cafe8ff3b21abd669b6cca90bb6d2b19457f41a64e02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab9c9e626f8605102041aa027ee23de6cc64819df9fd2c7745b0caedae9b9be4 0.600000000000 1396907 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": 938837, "vin": [ { "gen": { "height": 938827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab9c9e626f8605102041aa027ee23de6cc64819df9fd2c7745b0caedae9b9be4" } } ], "extra": [ 1, 209, 113, 55, 240, 3, 231, 248, 229, 214, 184, 9, 202, 254, 143, 243, 178, 26, 189, 102, 155, 108, 202, 144, 187, 109, 43, 25, 69, 127, 65, 166, 78, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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