Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 789fa6893ab3f64c93bb3dd603394e053b92ff7ab48ca103e3fcd6abe2a282d4

Tx prefix hash: 160fff24fcc9c2d092aa2fa94db5e9f60561e4a62a737a5d7ce521f55779dc02
Tx public key: c6458b74fa3f147b286513870a410f42311f7c58892ec48643048ffd7185e2cf
Timestamp: 1682502413 Timestamp [UCT]: 2023-04-26 09:46:53 Age [y:d:h:m:s]: 01:313:01:58:23
Block: 746934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484998 RingCT/type: yes/0
Extra: 01c6458b74fa3f147b286513870a410f42311f7c58892ec48643048ffd7185e2cf021100000004e7ace25d000000000000000000

1 output(s) for total of 2.056353613000 dcy

stealth address amount amount idx
00: 4bdde6a0dfcdfafc4aced8f287dfd931e9cc0b541ca0a780cbe1663e26091ad6 2.056353613000 1194543 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": 746944, "vin": [ { "gen": { "height": 746934 } } ], "vout": [ { "amount": 2056353613, "target": { "key": "4bdde6a0dfcdfafc4aced8f287dfd931e9cc0b541ca0a780cbe1663e26091ad6" } } ], "extra": [ 1, 198, 69, 139, 116, 250, 63, 20, 123, 40, 101, 19, 135, 10, 65, 15, 66, 49, 31, 124, 88, 137, 46, 196, 134, 67, 4, 143, 253, 113, 133, 226, 207, 2, 17, 0, 0, 0, 4, 231, 172, 226, 93, 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