Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d52768fbd0b4683125a003dd2d5b4aa745bf00eb734246eca010aa4bb462bae

Tx prefix hash: 074e35e10928bba4e00cc3edbe140d946ec78017f8b71b8362cac39b7607b1e5
Tx public key: 07876d6baeb3be2e4667eecb26d6dc69da45f3c2676c2f319b8c5a22cf0b6616
Timestamp: 1702978064 Timestamp [UCT]: 2023-12-19 09:27:44 Age [y:d:h:m:s]: 01:327:15:05:45
Block: 916439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493006 RingCT/type: yes/0
Extra: 0107876d6baeb3be2e4667eecb26d6dc69da45f3c2676c2f319b8c5a22cf0b661602110000000a33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fabd29f8240c691cf54be5d79d578f53b1a01066761845a380859bdf49b3303 0.600000000000 1373991 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": 916449, "vin": [ { "gen": { "height": 916439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fabd29f8240c691cf54be5d79d578f53b1a01066761845a380859bdf49b3303" } } ], "extra": [ 1, 7, 135, 109, 107, 174, 179, 190, 46, 70, 103, 238, 203, 38, 214, 220, 105, 218, 69, 243, 194, 103, 108, 47, 49, 155, 140, 90, 34, 207, 11, 102, 22, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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