Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c45fec1b9c1226e459157394404b2c9de7ac31d696009b1364a28b47cd016b1

Tx prefix hash: 405c6f92024bb7fc4f15dd4333c8db443131c09eb829fce1333b68011cdac872
Tx public key: 6c20db287624453427b7c7c6edb390c7349b1dfc6716fcb0f753ea0ef8870c61
Timestamp: 1733204259 Timestamp [UCT]: 2024-12-03 05:37:39 Age [y:d:h:m:s]: 00:124:06:13:54
Block: 1166922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88612 RingCT/type: yes/0
Extra: 016c20db287624453427b7c7c6edb390c7349b1dfc6716fcb0f753ea0ef8870c610211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b43421b2d55ca24d6d1a0f3d6b465be57986a5b52b37651a562d4aa4801f90df 0.600000000000 1652615 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": 1166932, "vin": [ { "gen": { "height": 1166922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b43421b2d55ca24d6d1a0f3d6b465be57986a5b52b37651a562d4aa4801f90df" } } ], "extra": [ 1, 108, 32, 219, 40, 118, 36, 69, 52, 39, 183, 199, 198, 237, 179, 144, 199, 52, 155, 29, 252, 103, 22, 252, 176, 247, 83, 234, 14, 248, 135, 12, 97, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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