Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f52838c68df2e1fd0c35860fb03e27f02c24935b95ae38e4b49f39cc3b384f4

Tx prefix hash: 74e844a816111dfa3e1c287e5fe643a3ee1b724e62bd79f3c0bab50d3a9dd18c
Tx public key: 063a291a11ec621f321505cdac8086bf462efd0ef220b29e18ee998ea9db05a4
Timestamp: 1577575754 Timestamp [UTC]: 2019-12-28 23:29:14 Age [y:d:h:m:s]: 06:053:03:41:55
Block: 33907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1446138 RingCT/type: yes/0
Extra: 01063a291a11ec621f321505cdac8086bf462efd0ef220b29e18ee998ea9db05a40211000000034ac5aa02000000000000000000

1 output(s) for total of 0.473871278743 xmr

stealth address amount amount idx tag
00: 6b486821400f0ca958baf573d4cfaeb2ebae06e3199dbb40880b0a78b13ebce4 0.473871278743 56953 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 dinastycoin-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": 33917, "vin": [ { "gen": { "height": 33907 } } ], "vout": [ { "amount": 473871278743, "target": { "key": "6b486821400f0ca958baf573d4cfaeb2ebae06e3199dbb40880b0a78b13ebce4" } } ], "extra": [ 1, 6, 58, 41, 26, 17, 236, 98, 31, 50, 21, 5, 205, 172, 128, 134, 191, 70, 46, 253, 14, 242, 32, 178, 158, 24, 238, 153, 142, 169, 219, 5, 164, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369