Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 486ce01923875fee0609c028fc66b7309de2517e3baf3b96eb59980b9e5d88be

Tx prefix hash: 976367321de10b7a614afc7218673ed50db4d08577c37b2e6e2fcdbbebb9deb7
Tx public key: 0e3112ba59898add55d91de6cbe9e2dce3611e726e5ff50e08a7319b9a3a58a5
Timestamp: 1724051950 Timestamp [UCT]: 2024-08-19 07:19:10 Age [y:d:h:m:s]: 00:263:02:29:56
Block: 1091150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187930 RingCT/type: yes/0
Extra: 010e3112ba59898add55d91de6cbe9e2dce3611e726e5ff50e08a7319b9a3a58a5021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da63ae8fe365c830ea11f7954296700aa91b4fe4dd9ff0888ce4072f8bdf6108 0.600000000000 1565779 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": 1091160, "vin": [ { "gen": { "height": 1091150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da63ae8fe365c830ea11f7954296700aa91b4fe4dd9ff0888ce4072f8bdf6108" } } ], "extra": [ 1, 14, 49, 18, 186, 89, 137, 138, 221, 85, 217, 29, 230, 203, 233, 226, 220, 227, 97, 30, 114, 110, 95, 245, 14, 8, 167, 49, 155, 154, 58, 88, 165, 2, 17, 0, 0, 0, 3, 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