Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 755befbbcd3a1b42a5efdedbaf11135a636b5187150b8413b04ef46969ecec21

Tx prefix hash: 13706b2046d84622613c0fd26a6a7bf9bb14a797306859a91a2ba137b49e2f3c
Tx public key: 642a276fea596fd3189acbf37aad3b1db2407d1da0c4433a78fb3e90afe9068f
Timestamp: 1710545368 Timestamp [UCT]: 2024-03-15 23:29:28 Age [y:d:h:m:s]: 00:344:07:26:14
Block: 979184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246136 RingCT/type: yes/0
Extra: 01642a276fea596fd3189acbf37aad3b1db2407d1da0c4433a78fb3e90afe9068f02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cb4f83cb267fe5c5d13f9d2a4ac6b33f4ca25cc9bb5335143bc32916738afd3 0.600000000000 1439217 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": 979194, "vin": [ { "gen": { "height": 979184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cb4f83cb267fe5c5d13f9d2a4ac6b33f4ca25cc9bb5335143bc32916738afd3" } } ], "extra": [ 1, 100, 42, 39, 111, 234, 89, 111, 211, 24, 154, 203, 243, 122, 173, 59, 29, 178, 64, 125, 29, 160, 196, 67, 58, 120, 251, 62, 144, 175, 233, 6, 143, 2, 17, 0, 0, 0, 7, 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