Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c57d82e410c95c13c39cec9da27389951c10f03f7f4595ab7ba0303e5749e062

Tx prefix hash: 72fe8ffa456631fd36aedf423eb7bb9d34b1d12b1662018bd29bb567cf2f8ae9
Tx public key: 052d55b21b7cd69fa993d9c6dbb150eab35d0a18ba373b58aee4339fbb60d24b
Timestamp: 1706257768 Timestamp [UCT]: 2024-01-26 08:29:28 Age [y:d:h:m:s]: 01:030:12:02:53
Block: 943603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282854 RingCT/type: yes/0
Extra: 01052d55b21b7cd69fa993d9c6dbb150eab35d0a18ba373b58aee4339fbb60d24b0211000000020c35fb00000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46aaae2afbd0714fe9cea857b958d9a0643095d207532a2f75e16878285d4aa4 0.600000000000 1401811 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": 943613, "vin": [ { "gen": { "height": 943603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46aaae2afbd0714fe9cea857b958d9a0643095d207532a2f75e16878285d4aa4" } } ], "extra": [ 1, 5, 45, 85, 178, 27, 124, 214, 159, 169, 147, 217, 198, 219, 177, 80, 234, 179, 93, 10, 24, 186, 55, 59, 88, 174, 228, 51, 159, 187, 96, 210, 75, 2, 17, 0, 0, 0, 2, 12, 53, 251, 0, 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