Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bfb61558195d85be69689074bb4d4702fa04c70584056e238f24839a3f3b3c9

Tx prefix hash: 41983ac8dd47eee4cecb4c162f47834a051fb026ada6944e21bea4a1a11a7890
Tx public key: 8b565bf195a6355e047f0fd7bb6e96efa7d20137775856a6340b77f2c809df62
Timestamp: 1722548034 Timestamp [UCT]: 2024-08-01 21:33:54 Age [y:d:h:m:s]: 00:239:07:05:20
Block: 1078675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170923 RingCT/type: yes/0
Extra: 018b565bf195a6355e047f0fd7bb6e96efa7d20137775856a6340b77f2c809df62021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2e38d4053c07f6cef8883a2f11ff93cb8e2544a63276107d0186ce911aea2b6 0.600000000000 1551306 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": 1078685, "vin": [ { "gen": { "height": 1078675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2e38d4053c07f6cef8883a2f11ff93cb8e2544a63276107d0186ce911aea2b6" } } ], "extra": [ 1, 139, 86, 91, 241, 149, 166, 53, 94, 4, 127, 15, 215, 187, 110, 150, 239, 167, 210, 1, 55, 119, 88, 86, 166, 52, 11, 119, 242, 200, 9, 223, 98, 2, 17, 0, 0, 0, 4, 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