Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82d19cd605afe617ea2142185cb09ddd18999f371f925b545f06e69adb195fcb

Tx prefix hash: 316a5306870ad0e9997134087a315c956774978e6999df2f434df52e3ca4de17
Tx public key: d8cd4759a7071e36f0c7902f90da9ae0a3513869b8ccbbdc63da118425cbf8e8
Timestamp: 1702348427 Timestamp [UCT]: 2023-12-12 02:33:47 Age [y:d:h:m:s]: 01:157:11:51:33
Block: 911220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373723 RingCT/type: yes/0
Extra: 01d8cd4759a7071e36f0c7902f90da9ae0a3513869b8ccbbdc63da118425cbf8e8021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e01e297c447b7b599470e8f909f4b559bc1c66e5aeb323287278cb595fd4ebd 0.600000000000 1368401 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": 911230, "vin": [ { "gen": { "height": 911220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e01e297c447b7b599470e8f909f4b559bc1c66e5aeb323287278cb595fd4ebd" } } ], "extra": [ 1, 216, 205, 71, 89, 167, 7, 30, 54, 240, 199, 144, 47, 144, 218, 154, 224, 163, 81, 56, 105, 184, 204, 187, 220, 99, 218, 17, 132, 37, 203, 248, 232, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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