Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f88f872c2327fb8c7b9c7c650f2b00a88b6a4f18c1834a4775d04ba0c1a94fc

Tx prefix hash: defac383114e03ca51ffdeb09c4c1ec2f886b760d8baf92f1f52d141e417cc16
Tx public key: eb323b20ab8e0823b175191cde50076c6de6b4abfe1e078a2111688c027d5bab
Timestamp: 1696821242 Timestamp [UCT]: 2023-10-09 03:14:02 Age [y:d:h:m:s]: 01:185:19:24:52
Block: 865597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393844 RingCT/type: yes/0
Extra: 01eb323b20ab8e0823b175191cde50076c6de6b4abfe1e078a2111688c027d5bab02110000000441ee1c9b000000000000000000

1 output(s) for total of 0.831606445000 dcy

stealth address amount amount idx
00: 118b173dcd4c93e3785eecdd3668e8b466f10146917bb29ec494a71724f076ce 0.831606445000 1320135 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": 865607, "vin": [ { "gen": { "height": 865597 } } ], "vout": [ { "amount": 831606445, "target": { "key": "118b173dcd4c93e3785eecdd3668e8b466f10146917bb29ec494a71724f076ce" } } ], "extra": [ 1, 235, 50, 59, 32, 171, 142, 8, 35, 177, 117, 25, 28, 222, 80, 7, 108, 109, 230, 180, 171, 254, 30, 7, 138, 33, 17, 104, 140, 2, 125, 91, 171, 2, 17, 0, 0, 0, 4, 65, 238, 28, 155, 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