Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6c46af52f833737ce399fd9a0556d757601fb45ff4ef2a6077024eac533d91e

Tx prefix hash: c7094c0c1191f7f44d65282e8f2172605af06d06da970fe72a00212e105cac2f
Tx public key: b3eb1c1241b606482ef807fca68db9c35959f8cf0b47d403c09b29c2e208a1f0
Timestamp: 1724009480 Timestamp [UCT]: 2024-08-18 19:31:20 Age [y:d:h:m:s]: 00:226:07:38:47
Block: 1090804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161602 RingCT/type: yes/0
Extra: 01b3eb1c1241b606482ef807fca68db9c35959f8cf0b47d403c09b29c2e208a1f002110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f2626b06e24cfc495cdcff1abe6b1584c7911a5d58c0f2594e2178e27906d43 0.600000000000 1565429 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": 1090814, "vin": [ { "gen": { "height": 1090804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f2626b06e24cfc495cdcff1abe6b1584c7911a5d58c0f2594e2178e27906d43" } } ], "extra": [ 1, 179, 235, 28, 18, 65, 182, 6, 72, 46, 248, 7, 252, 166, 141, 185, 195, 89, 89, 248, 207, 11, 71, 212, 3, 192, 155, 41, 194, 226, 8, 161, 240, 2, 17, 0, 0, 0, 12, 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