Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec2df099351428398d2079506a4b032640ecda64102055923fd074cfd469c73e

Tx prefix hash: eaf0460544b6690b0d836d3d63139e92ffe60c39d53fa7bef48c77bbb5f5bb57
Tx public key: bc7c7d04a8a1ede31e4df256ab6435f498287a437a08e1195c922679a035e8d6
Timestamp: 1718779985 Timestamp [UCT]: 2024-06-19 06:53:05 Age [y:d:h:m:s]: 01:150:05:28:41
Block: 1047445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365927 RingCT/type: yes/0
Extra: 01bc7c7d04a8a1ede31e4df256ab6435f498287a437a08e1195c922679a035e8d60211000000030bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c07354e15754df4c6dceb24d348f3b2ae1a792ca5f3b715fe940e6c36fa10dc 0.600000000000 1517272 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": 1047455, "vin": [ { "gen": { "height": 1047445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c07354e15754df4c6dceb24d348f3b2ae1a792ca5f3b715fe940e6c36fa10dc" } } ], "extra": [ 1, 188, 124, 125, 4, 168, 161, 237, 227, 30, 77, 242, 86, 171, 100, 53, 244, 152, 40, 122, 67, 122, 8, 225, 25, 92, 146, 38, 121, 160, 53, 232, 214, 2, 17, 0, 0, 0, 3, 11, 186, 22, 215, 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