Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b935b6176d04c1d256ff5b5caf99a1c87f1fee4028fe5a761a251a666dc76158

Tx prefix hash: 91cd51575979e11b89e5b17ca0bea4ea025d5af489e17d7ae0decaa646094bc4
Tx public key: eebc8d5a1ae97ea14ed95a6273705feb61b08cc29e32acbd092813cb12954903
Timestamp: 1725138493 Timestamp [UCT]: 2024-08-31 21:08:13 Age [y:d:h:m:s]: 00:130:08:38:12
Block: 1100147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93252 RingCT/type: yes/0
Extra: 01eebc8d5a1ae97ea14ed95a6273705feb61b08cc29e32acbd092813cb12954903021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87bddd8228dfefd5309d2dddd7d50f7ee266de6b4b426ab076a64d0a1bcd93e8 0.600000000000 1576120 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": 1100157, "vin": [ { "gen": { "height": 1100147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87bddd8228dfefd5309d2dddd7d50f7ee266de6b4b426ab076a64d0a1bcd93e8" } } ], "extra": [ 1, 238, 188, 141, 90, 26, 233, 126, 161, 78, 217, 90, 98, 115, 112, 95, 235, 97, 176, 140, 194, 158, 50, 172, 189, 9, 40, 19, 203, 18, 149, 73, 3, 2, 17, 0, 0, 0, 2, 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