Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa24722f156b5158db0dea5f2443a61f88cb229914ca9428a4e78dbf06fb11b4

Tx prefix hash: a5564572a73a0cd4f4077053b5b89d6b81f44505d14ddd5099eeedc7a69f655c
Tx public key: 8ccdc6694932b38b081bd099675d22aea4d5ccb1f3f180f604c2bca8186ab15b
Timestamp: 1709803794 Timestamp [UCT]: 2024-03-07 09:29:54 Age [y:d:h:m:s]: 01:271:14:08:31
Block: 973030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452853 RingCT/type: yes/0
Extra: 018ccdc6694932b38b081bd099675d22aea4d5ccb1f3f180f604c2bca8186ab15b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d919c0291c9487e950920e4743c35820793bbe5a6573f8bf29736e4a8300f67c 0.600000000000 1432959 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": 973040, "vin": [ { "gen": { "height": 973030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d919c0291c9487e950920e4743c35820793bbe5a6573f8bf29736e4a8300f67c" } } ], "extra": [ 1, 140, 205, 198, 105, 73, 50, 179, 139, 8, 27, 208, 153, 103, 93, 34, 174, 164, 213, 204, 177, 243, 241, 128, 246, 4, 194, 188, 168, 24, 106, 177, 91, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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