Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60c17f3db0ab5c6403dea951dce02fb03ac53b873e4723cd4bdb1d3e2633dfb2

Tx prefix hash: c6e223b7294ab843d3d323701bef20403b980fb1c9412b94fb79a0f257417a4f
Tx public key: c56d20403c95a33f1e69289fed1891c1e5158d206042ef513266521c417413bc
Timestamp: 1685904045 Timestamp [UCT]: 2023-06-04 18:40:45 Age [y:d:h:m:s]: 02:017:23:04:41
Block: 775129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534780 RingCT/type: yes/0
Extra: 01c56d20403c95a33f1e69289fed1891c1e5158d206042ef513266521c417413bc021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.658349324000 dcy

stealth address amount amount idx
00: d1959c96083a614c5d88e5c4a782e659b619a4f5606619f80d7dd24322ce1d27 1.658349324000 1224630 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": 775139, "vin": [ { "gen": { "height": 775129 } } ], "vout": [ { "amount": 1658349324, "target": { "key": "d1959c96083a614c5d88e5c4a782e659b619a4f5606619f80d7dd24322ce1d27" } } ], "extra": [ 1, 197, 109, 32, 64, 60, 149, 163, 63, 30, 105, 40, 159, 237, 24, 145, 193, 229, 21, 141, 32, 96, 66, 239, 81, 50, 102, 82, 28, 65, 116, 19, 188, 2, 17, 0, 0, 0, 1, 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