Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1443c1620dd6a145e88f0b18e0fbec13f51d02c53183cac6c994a81343c25505

Tx prefix hash: 00a860596cd6b7dd5d06285e103ad6583ab8a057ce1eaa54ce9207185b50f816
Tx public key: 484b65070d64a1fd39486dfecfb6fb47a74a570804b39f33e349465363a2b18b
Timestamp: 1701014007 Timestamp [UCT]: 2023-11-26 15:53:27 Age [y:d:h:m:s]: 01:089:00:26:39
Block: 900148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324743 RingCT/type: yes/0
Extra: 01484b65070d64a1fd39486dfecfb6fb47a74a570804b39f33e349465363a2b18b021100000001faf35c9c000000000000000000

1 output(s) for total of 0.638904563000 dcy

stealth address amount amount idx
00: 91c967efe9e065830766b7ac39d991c8d5ec7f758415e303326cb1d2285723d9 0.638904563000 1356625 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": 900158, "vin": [ { "gen": { "height": 900148 } } ], "vout": [ { "amount": 638904563, "target": { "key": "91c967efe9e065830766b7ac39d991c8d5ec7f758415e303326cb1d2285723d9" } } ], "extra": [ 1, 72, 75, 101, 7, 13, 100, 161, 253, 57, 72, 109, 254, 207, 182, 251, 71, 167, 74, 87, 8, 4, 179, 159, 51, 227, 73, 70, 83, 99, 162, 177, 139, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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