Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11e43fb60505edfefd04b8f2d1669e2e8b69cffe85f6d1cb8e87efbe15cbdbc7

Tx prefix hash: 7575b4b8ff8bd01a6cefc440d632f90ded381724407ad2e8143dabe194ae1c3d
Tx public key: 0c3cb8cd95ef48a42c86c7301b4e6d4dd40de7ce5a100a9e9a348abccc0709d3
Timestamp: 1725460520 Timestamp [UCT]: 2024-09-04 14:35:20 Age [y:d:h:m:s]: 00:214:21:06:00
Block: 1102835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153407 RingCT/type: yes/0
Extra: 010c3cb8cd95ef48a42c86c7301b4e6d4dd40de7ce5a100a9e9a348abccc0709d3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae4618a3d0a0811a634a4680ea57b7a65b650eb7a1bd7382115b4cbcf774a87c 0.600000000000 1579422 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": 1102845, "vin": [ { "gen": { "height": 1102835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae4618a3d0a0811a634a4680ea57b7a65b650eb7a1bd7382115b4cbcf774a87c" } } ], "extra": [ 1, 12, 60, 184, 205, 149, 239, 72, 164, 44, 134, 199, 48, 27, 78, 109, 77, 212, 13, 231, 206, 90, 16, 10, 158, 154, 52, 138, 188, 204, 7, 9, 211, 2, 17, 0, 0, 0, 2, 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