Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cfe4d400263b692e9a0e33b8482ad0ec90220a65ca3cc446f63fd1524fcef1c

Tx prefix hash: c37f3cbf47697b42d61d39dacfefaeee41846e1e6c93d5165af62b0603ee8af5
Tx public key: cfa1f42367ef2206e070015daa3fe43532acb2793974188c23a15411a3b096f6
Timestamp: 1578269220 Timestamp [UCT]: 2020-01-06 00:07:00 Age [y:d:h:m:s]: 04:331:20:12:14
Block: 39509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126434 RingCT/type: yes/0
Extra: 01cfa1f42367ef2206e070015daa3fe43532acb2793974188c23a15411a3b096f6021100000001bd0f9f9f000000000000000000

1 output(s) for total of 454.036879697000 dcy

stealth address amount amount idx
00: ccbcc4a1a6b42c4e5b7a3313643453bee386819c0b946805fcc3d564ba38d728 454.036879697000 68293 of 0

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": 39519, "vin": [ { "gen": { "height": 39509 } } ], "vout": [ { "amount": 454036879697, "target": { "key": "ccbcc4a1a6b42c4e5b7a3313643453bee386819c0b946805fcc3d564ba38d728" } } ], "extra": [ 1, 207, 161, 244, 35, 103, 239, 34, 6, 224, 112, 1, 93, 170, 63, 228, 53, 50, 172, 178, 121, 57, 116, 24, 140, 35, 161, 84, 17, 163, 176, 150, 246, 2, 17, 0, 0, 0, 1, 189, 15, 159, 159, 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