Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe4473b0144408178c3ea7785b80892c700b3329ae44eff4b8b57be4ede33673

Tx prefix hash: b44bede44b54e8bed80d4f2855d26a86762b295186c79f13e0505b146e0df2f3
Tx public key: f2767b49b33e806249c8b7914262ac95a613ef987c64ccfd2b139f311bd182f3
Timestamp: 1672985578 Timestamp [UCT]: 2023-01-06 06:12:58 Age [y:d:h:m:s]: 02:134:13:46:31
Block: 668651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 617882 RingCT/type: yes/0
Extra: 01f2767b49b33e806249c8b7914262ac95a613ef987c64ccfd2b139f311bd182f302110000000933af99f4000000000000000000

1 output(s) for total of 3.736643162000 dcy

stealth address amount amount idx
00: 46e4afe44af3d6c6288fbd32f52ef484ecf3ed0f043d49847a18fb59c4dbc3ef 3.736643162000 1109908 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": 668661, "vin": [ { "gen": { "height": 668651 } } ], "vout": [ { "amount": 3736643162, "target": { "key": "46e4afe44af3d6c6288fbd32f52ef484ecf3ed0f043d49847a18fb59c4dbc3ef" } } ], "extra": [ 1, 242, 118, 123, 73, 179, 62, 128, 98, 73, 200, 183, 145, 66, 98, 172, 149, 166, 19, 239, 152, 124, 100, 204, 253, 43, 19, 159, 49, 27, 209, 130, 243, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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