Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eff02c586bbcf164475b98085a277ca72184fb9fccc8067297160fa342557d16

Tx prefix hash: 950f19595520bf6fb3f0aa1c6511d13a3b2a331b12a58b57fc3a7f058fe71048
Tx public key: 5960c4fefc3c8ba8edf8bca98eac6476dc80566634c0c58a35acfd42d380e3f4
Timestamp: 1733239625 Timestamp [UCT]: 2024-12-03 15:27:05 Age [y:d:h:m:s]: 00:118:05:53:47
Block: 1167222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84299 RingCT/type: yes/0
Extra: 015960c4fefc3c8ba8edf8bca98eac6476dc80566634c0c58a35acfd42d380e3f4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c133ded04c01fa236e239d7e9877d0c1945162f8c5861a848fc761f0a70e88f3 0.600000000000 1652917 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": 1167232, "vin": [ { "gen": { "height": 1167222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c133ded04c01fa236e239d7e9877d0c1945162f8c5861a848fc761f0a70e88f3" } } ], "extra": [ 1, 89, 96, 196, 254, 252, 60, 139, 168, 237, 248, 188, 169, 142, 172, 100, 118, 220, 128, 86, 102, 52, 192, 197, 138, 53, 172, 253, 66, 211, 128, 227, 244, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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