Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 483f5152bfde0c68871a5afa37d7e560d44015c0d1f553715daf9517e60b5fef

Tx prefix hash: fb950d0f01b6d43d97a66352c3752726876365f33ea0effd947b2b03d245da70
Tx public key: a1cc0c9b0a54904debb3e0336ac621fd168c3b530830d158cceb263b833cea8f
Timestamp: 1720777128 Timestamp [UCT]: 2024-07-12 09:38:48 Age [y:d:h:m:s]: 00:271:02:15:44
Block: 1064011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193677 RingCT/type: yes/0
Extra: 01a1cc0c9b0a54904debb3e0336ac621fd168c3b530830d158cceb263b833cea8f02110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39475cf2a59e6b288410347fe501a1a49bd8c7c55766d055f7e95a2d6dc55043 0.600000000000 1534532 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": 1064021, "vin": [ { "gen": { "height": 1064011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39475cf2a59e6b288410347fe501a1a49bd8c7c55766d055f7e95a2d6dc55043" } } ], "extra": [ 1, 161, 204, 12, 155, 10, 84, 144, 77, 235, 179, 224, 51, 106, 198, 33, 253, 22, 140, 59, 83, 8, 48, 209, 88, 204, 235, 38, 59, 131, 60, 234, 143, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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