Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ada988aa04a3f51db2addba7d96d2d2225d510162c4d7c070ed01c5f52f97dcc

Tx prefix hash: 0b7775718e15d804ed3b12dc004a589ec9067b2e9c188e2d2fe7a857c70f4361
Tx public key: 5e4933d7b42bd65c8e28655b8d58e9dce423389ec9a71d6fbdb518df4c8da53a
Timestamp: 1708266477 Timestamp [UCT]: 2024-02-18 14:27:57 Age [y:d:h:m:s]: 01:291:08:00:33
Block: 960275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466997 RingCT/type: yes/0
Extra: 015e4933d7b42bd65c8e28655b8d58e9dce423389ec9a71d6fbdb518df4c8da53a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0cf8b0fd0bfc240bfb1b5fdcaaae457c1270830f0f2d146050079f15598fbcb 0.600000000000 1419838 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": 960285, "vin": [ { "gen": { "height": 960275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0cf8b0fd0bfc240bfb1b5fdcaaae457c1270830f0f2d146050079f15598fbcb" } } ], "extra": [ 1, 94, 73, 51, 215, 180, 43, 214, 92, 142, 40, 101, 91, 141, 88, 233, 220, 228, 35, 56, 158, 201, 167, 29, 111, 189, 181, 24, 223, 76, 141, 165, 58, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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