Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efae50785cddf457a18231dc4b0670a2f85fa7767a6e11833f37b1da847dc301

Tx prefix hash: 7fd6c355866c5b336b52329837dd36dc5a81a4148593320e365bc6c52dc501cc
Tx public key: a41f0d4d8d00e00de8bfa488e0dce160cf8f75ef824946e2a1499dd029c0ba88
Timestamp: 1694472406 Timestamp [UCT]: 2023-09-11 22:46:46 Age [y:d:h:m:s]: 01:260:03:45:18
Block: 846103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447078 RingCT/type: yes/0
Extra: 01a41f0d4d8d00e00de8bfa488e0dce160cf8f75ef824946e2a1499dd029c0ba8802110000000de6d27f9c000000000000000000

1 output(s) for total of 0.964960618000 dcy

stealth address amount amount idx
00: cba1686162e27888017de4ab1d1f15cd4995b74b89258a36010baed2185e3358 0.964960618000 1299545 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": 846113, "vin": [ { "gen": { "height": 846103 } } ], "vout": [ { "amount": 964960618, "target": { "key": "cba1686162e27888017de4ab1d1f15cd4995b74b89258a36010baed2185e3358" } } ], "extra": [ 1, 164, 31, 13, 77, 141, 0, 224, 13, 232, 191, 164, 136, 224, 220, 225, 96, 207, 143, 117, 239, 130, 73, 70, 226, 161, 73, 157, 208, 41, 192, 186, 136, 2, 17, 0, 0, 0, 13, 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