Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ec115f97c670b215082b833b3fdf7aa09cdddd454b2b7dcf659665fca0eccc

Tx prefix hash: 06423e621c77eeea7d1227ddce138cd0889aff0af4cc1f9fb86b7739f9991a60
Tx public key: 4ce9503212328da4976ff3df37f399bc6aae754f102c39e2120cc70cceedfb7d
Timestamp: 1717553542 Timestamp [UCT]: 2024-06-05 02:12:22 Age [y:d:h:m:s]: 00:180:06:37:28
Block: 1037278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129029 RingCT/type: yes/0
Extra: 014ce9503212328da4976ff3df37f399bc6aae754f102c39e2120cc70cceedfb7d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7e4e55db1fd4d4470fdc8ea644d1c7fe0255fdd8f93f70e69b1bffaf63aec48 0.600000000000 1505809 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": 1037288, "vin": [ { "gen": { "height": 1037278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7e4e55db1fd4d4470fdc8ea644d1c7fe0255fdd8f93f70e69b1bffaf63aec48" } } ], "extra": [ 1, 76, 233, 80, 50, 18, 50, 141, 164, 151, 111, 243, 223, 55, 243, 153, 188, 106, 174, 117, 79, 16, 44, 57, 226, 18, 12, 199, 12, 206, 237, 251, 125, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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