Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8075cf48b3b4226a65bf035fc808a8d1ff50aee4f29d3d71a5d5808b53f5f166

Tx prefix hash: 1d4b5479c31caa7ebe253376583724ad354234b6b90048a8eed04fdbf790e437
Tx public key: 02b6ff2221c27df2d72f7b091e684097bbbb4328d841cec6dbb73a35e3f120f0
Timestamp: 1742906694 Timestamp [UCT]: 2025-03-25 12:44:54 Age [y:d:h:m:s]: 00:254:20:43:17
Block: 1246979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179921 RingCT/type: yes/0
Extra: 0102b6ff2221c27df2d72f7b091e684097bbbb4328d841cec6dbb73a35e3f120f002110000000124ff4ea1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93e1eb25d4d1d7f59e4028610da4d9db69b146423c8acd1fe1747bc000254517 0.600000000000 1733980 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": 1246989, "vin": [ { "gen": { "height": 1246979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93e1eb25d4d1d7f59e4028610da4d9db69b146423c8acd1fe1747bc000254517" } } ], "extra": [ 1, 2, 182, 255, 34, 33, 194, 125, 242, 215, 47, 123, 9, 30, 104, 64, 151, 187, 187, 67, 40, 216, 65, 206, 198, 219, 183, 58, 53, 227, 241, 32, 240, 2, 17, 0, 0, 0, 1, 36, 255, 78, 161, 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