Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cd16c2de9af68d54b65a4fdef5166ae2ae820493725764caf23383df2dff1c2

Tx prefix hash: 7b19f4041a6f093018d77a3a2cd58747143d61c03de4137cd940f080941dedb5
Tx public key: b280b0ad6096dcc666a1d60ffbf665bdee7c2717d7418bd42aaa9d690a3cd9df
Timestamp: 1718601709 Timestamp [UCT]: 2024-06-17 05:21:49 Age [y:d:h:m:s]: 00:191:14:19:44
Block: 1045960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137124 RingCT/type: yes/0
Extra: 01b280b0ad6096dcc666a1d60ffbf665bdee7c2717d7418bd42aaa9d690a3cd9df0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16aa3c73a3afed418482037b530ebc3e7a7f0abf0bb2c0e094784c3d29a68712 0.600000000000 1515687 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": 1045970, "vin": [ { "gen": { "height": 1045960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16aa3c73a3afed418482037b530ebc3e7a7f0abf0bb2c0e094784c3d29a68712" } } ], "extra": [ 1, 178, 128, 176, 173, 96, 150, 220, 198, 102, 161, 214, 15, 251, 246, 101, 189, 238, 124, 39, 23, 215, 65, 139, 212, 42, 170, 157, 105, 10, 60, 217, 223, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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