Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 500c242d55d9be87c60d6a464bb598dd43e4242945a03cbf1955a9f7a922eebe

Tx prefix hash: cd131d6076cf55a01f8cb5ec10a24afe8bbd25a93f2420b531d1520cf8d67b58
Tx public key: 42f3fec41c4a1d8e7b27212403bc3b7bc1a6d6412a81f437364f450b6b924430
Timestamp: 1734073922 Timestamp [UCT]: 2024-12-13 07:12:02 Age [y:d:h:m:s]: 00:096:11:01:54
Block: 1174153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68718 RingCT/type: yes/0
Extra: 0142f3fec41c4a1d8e7b27212403bc3b7bc1a6d6412a81f437364f450b6b924430021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e5404b1caeccb6419966697066c2b2da357ec298823bd8df5cbd40c3cbabdcc 0.600000000000 1660268 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": 1174163, "vin": [ { "gen": { "height": 1174153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e5404b1caeccb6419966697066c2b2da357ec298823bd8df5cbd40c3cbabdcc" } } ], "extra": [ 1, 66, 243, 254, 196, 28, 74, 29, 142, 123, 39, 33, 36, 3, 188, 59, 123, 193, 166, 214, 65, 42, 129, 244, 55, 54, 79, 69, 11, 107, 146, 68, 48, 2, 17, 0, 0, 0, 3, 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