Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb8be6e3f690901fcdf508caa65e1494b39969e35f403bf278d122b22e2a4fe3

Tx prefix hash: 40900c8494670c9fdf391999935ae912a0982a57de9eff7a4e3e14b4a0b5ee26
Tx public key: ca83b3ac1e666a6958186b3700839f68d2635ba1467b4b6a8396708783f2915f
Timestamp: 1617068224 Timestamp [UCT]: 2021-03-30 01:37:04 Age [y:d:h:m:s]: 03:337:06:27:46
Block: 229379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1000291 RingCT/type: yes/0
Extra: 01ca83b3ac1e666a6958186b3700839f68d2635ba1467b4b6a8396708783f2915f0211000000667071732b000000000000000000

1 output(s) for total of 106.652916431000 dcy

stealth address amount amount idx
00: 708638679087760bf60e3b9ddc0e1316f3c60501e18f3d3b999a10e27e7dfc46 106.652916431000 475919 of 0

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": 229389, "vin": [ { "gen": { "height": 229379 } } ], "vout": [ { "amount": 106652916431, "target": { "key": "708638679087760bf60e3b9ddc0e1316f3c60501e18f3d3b999a10e27e7dfc46" } } ], "extra": [ 1, 202, 131, 179, 172, 30, 102, 106, 105, 88, 24, 107, 55, 0, 131, 159, 104, 210, 99, 91, 161, 70, 123, 75, 106, 131, 150, 112, 135, 131, 242, 145, 95, 2, 17, 0, 0, 0, 102, 112, 113, 115, 43, 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